Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Compressed data is "corrupt^M" error while migrating Windows vCenter 6.0 with vPostgres DB to VCSA 6.5 (59342)

Last Updated: 8/6/2020Categories: TroubleshootingTotal Views: 5534Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Migration from windows vcenter 6.0  with vPostgres DB to 6.5 VCSA fails with error's similar to below:

No file found matching /etc/vmware/install-defaults/cm.url

No file found matching /etc/vmware-vpx/vcdb.properties

No file found matching /etc/vmware-vpx/vc-extn-cisreg.prop

cmd "/opt/vmware/bin/sso-config.sh get_identity_sources $VMWARE_LOG_DIR" timed out after 60 seconds due to lack of progress in last 30 seconds (0 bytes read)"

Cause

Error occurs due to table corruption in the Database. Log snipping matches to below :-

Upgrade EXPORT failed.

vcdb_export.err :-
pg_dump: NOTICE: there are circular foreign-key constraints among these table(s):
pg_dump:   vpx_entity
pg_dump: You might not be able to restore the dump without using --disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a --data-only dump to avoid this problem.
pg_dump: Dumping the contents of table "vpx_binary_data" failed: PQgetResult() failed.
pg_dump: Error message from server: ERROR:  compressed data is corrupt

upgrade-runner.log :-
2018-08-31T19:28:21.861Z INFO upgrade.states.component_states vcdb:Export: reported message 'Exporting VMware vCenter Server Database data...'
2018-08-31T19:28:21.862Z INFO upgrade.states.component_states vcdb:Export: 2018-08-31T19:28:21.318Z INFO vcdb.const Exporting core tables...
2018-08-31T19:28:22.871Z INFO upgrade.states.component_states vcdb:Export: ^M
2018-08-31T19:28:22.871Z INFO upgrade.states.component_states vcdb:Export: 2018-08-31T19:28:22.361Z ERROR vcdb.const Error while exporting source core tables: pg_dump: Error message from server: ERROR:  compressed data is corrupt^M
2018-08-31T19:28:22.871Z INFO upgrade.states.component_states vcdb:Export: ^M
2018-08-31T19:28:22.871Z INFO upgrade.states.component_states vcdb:Export: 2018-08-31T19:28:22.361Z ERROR __main__ Upgrade Phase 'vcdb:Export' failed. Exception: Error while exporting source core tables: pg_dump: Error message from server: ERROR:  compressed data is corrupt^M
.
2018-08-31T19:28:22.875Z INFO upgrade.states.component_states vcdb:Export: PermanentError: Error while exporting source core tables: pg_dump: Error message from server: ERROR:  compressed data is corrupt
2018-08-31T19:28:22.875Z INFO upgrade.states.component_states vcdb:Export: Script completed for 194.039999962 secs with return-code='1', and executionId=a4cd2f65-b88b-4764-a370-d2af385e22aa
2018-08-31T19:28:22.878Z ERROR upgrade.states.component_states vcdb:Export: Remote script failed with an error [PermanentError()]
2018-08-31T19:28:22.880Z ERROR upgrade.states.component_states vcdb:Export: failed with permanent error. For details take a look at Export_com.vmware.vcdb_2018_08_31_12_18.log.
2018-08-31T19:28:22.892Z WARNING wf.wf_processor State Export com.vmware.vcdb has failed.

Impact / Risks

vCenter migration fails

Resolution

To resolve this issue, perform the following steps:

1 - Identify the corrupt table from the logs entries. In this instance "Dumping the contents of table "vpx_binary_data" failed: PQgetResult() failed"
2 - Connect to VCDB using  SQL Management Studio.

Note: This procedure modifies the database. Ensure to take a valid backup of the database before proceeding.

3 - Run the commands:

Truncate table vpx_binary_data;

4 - Start the vCenter Server service.
5 - Start Migration process again

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Windows 2008 R2 ディスク ボリュームが読み取り専用になり、起動に失敗する (2001611)

KB
•
Windows 2008 R2 磁盘卷变为只读并且引导失败 (2001611)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 6.0.x

Take Our Survey

Support Assistant